ODF Release 1 introduces a "Part Info" resource that must be defined by all ODF parts. This resource contains information that were, in previous releases, passed to the FW_CPart constructor.
The Part Info resource looks like this (taken from ODFTable, PartInfo.fr):
//--------------------------------------
// PartInfo Resource
//--------------------------------------
resource FW_RPartInfo(kPartInfoID)
{
// ----- Icon ID
kViewAsIconID,
// ----- Part Name
kEditorUserString,
// ----- PartKind
kKind
};
The first field is the default icon ID used when a frame is viewed as an icon. You will usually reference the document icon defined in your BNDL resource. If you want to choose or create the icon dynamically, you can override FW_CFrame::GetIcon and provide a different icon.
The second field is the Editor User String. This is one of the strings, usually defined in your Binding.k file, used by your NMAP resources.
The last field is your part kind. This is also a string usually defined in your Binding.k file and used by your NMAP resources.
This resource MUST BE present. You will get an assertion if the resource is missing.
The reasons for this resource are:
- OpenDoc for Windows doesn't have NMAPs resources. It is not possible to find the Editor User String and Part Kind by looking at the NMAP resources
- Passing the Editor User String to the FW_CPart constructor was making localization impossible
- Future releases of ODF may add more fields to this resource so more default behaviors can be built into ODF. Good candidates are: the menu bar resource ID so ODF could automatically load your menu bar from resource, the About resource ID so you won't have to override your FW_CPart::DoMenu method just to present a standard About box.
